Add safe deterministic world processing - #77

Summary

• add deterministic, content-addressed Bedrock world processors
• verify staged mutations while keeping authored worlds immutable
• integrate processed worlds into development and packaging flows
• update archive, compiler, and LevelDB dependencies
• preserve caller-owned chunk coordinates at the mcbe-leveldb 1.21 compatibility boundary
• add the minor changeset for @blurengine/cli 0.15.0

Why

Projects need reproducible generated world data without mutating committed raw worlds or trusting ambiguous processor output.

Validation

• npm.cmd run check
• 295 tests passed
• build and package validation passed
• clean worktree and git diff --check

Dependency health

The current registry advisory feed reports 6 advisories (5 high, 1 critical). Four are in the optional native chain @8crafter/leveldb-zlib -> cmake-js -> tar; two are transitive development-tool advisories (brace-expansion and js-yaml). npm audit fix --dry-run produced no compatible lockfile change. The only suggested native-chain action is an invalid major downgrade to mcbe-leveldb 1.1.0, so no unsafe override or downgrade is included.